This is a comment left during a code review.
Path: sdks/typescript-sdk-cli/bin/t49.ts
Line: 12-13

Comment:
**`program.parse` will not await async command handlers**

All CLI commands will make HTTP requests via the SDK (async operations). Commander's `program.parse()` does **not** await async `.action()` handlers — they run as fire-and-forget Promises, meaning errors are silently swallowed and `process.exit` may be called before the async work completes.

This should use `parseAsync` at the entry point:

```suggestion
import { createProgram } from '../src/index.js';

const program = createProgram();
await program.parseAsync(process.argv);
```

Because of the top-level `await`, `bin/t49.ts` must also be compiled with a target/module that supports it (already satisfied by `"target": "ES2022"` + `"module": "NodeNext"`).

How can I resolve this? If you propose a fix, please make it concise.

This is a comment left during a code review.
Path: sdks/typescript-sdk-cli/src/index.ts
Line: 22

Comment:
**Hardcoded version will drift from `package.json`**

`.version('0.1.0')` duplicates the version from `package.json`. As the package is bumped these will diverge silently. Since `resolveJsonModule: true` is already set in `tsconfig.json`, the version can be imported directly:

```
import { createRequire } from 'node:module';
const require = createRequire(import.meta.url);
const { version } = require('../package.json');
```

Then replace the hardcoded string:
```suggestion
    .version(version)
```

How can I resolve this? If you propose a fix, please make it concise.

This is a comment left during a code review.
Path: sdks/typescript-sdk-cli/src/index.ts
Line: 24-29

Comment:
**`--raw` flag duplicates `--format raw`**

Line 24 adds a standalone `--raw` flag ("Output raw JSON:API document"), while line 29 adds `--format <format>` which already accepts `raw` as a valid value. These two flags represent the same output mode. Having both creates ambiguous precedence (what wins when `--raw` and `--format mapped` are both passed?) and will confuse both human users and LLM agents discovering the CLI via `t49 commands --json`.

Consider removing `--raw` and making `--format raw` the canonical way to request the raw JSON:API document.

How can I resolve this? If you propose a fix, please make it concise.

This is a comment left during a code review.
Path: sdks/typescript-sdk-cli/src/index.ts
Line: 21-23

Comment:
**`--json` and `--table` are mutually exclusive but not enforced**

Both `--json` and `--table` can be passed simultaneously. Commander does not auto-detect conflicting flags, so the formatter will receive both as `true` with no clear winner. Even as a scaffold, adding a note or using a Commander `.addOption` with `.conflicts()` will prevent future confusion:

```ts
.addOption(new Option('--json', 'Force JSON output').conflicts('table'))
.addOption(new Option('--table', 'Force table output').conflicts('json'))
```

How can I resolve this? If you propose a fix, please make it concise.

This is a comment left during a code review.
Path: sdks/typescript-sdk-cli/package.json
Line: 46-47

Comment:
**`vitest` version pinned to `^4.0.13` — verify this is intentional**

Vitest `^4.x` is a very recent major release. Confirm this version is available and stable in your environment; the `^` range will pick up any `4.x` patch/minor automatically, which may be fine, but it is worth validating the major version bump from the more widely-used `^2.x` series is deliberate and that the API used in `vitest.config.ts` (`configDefaults`, `defineConfig`) is still compatible.

How can I resolve this? If you propose a fix, please make it concise.